Skip to content

Fix regression bug with notification type enqueuing as separate notification #138

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
May 27, 2025

Conversation

stephen-cox
Copy link
Member

Fixes #137

What does this change?

Enqueues notifications depending on service contact and notification type, not just on service contact

With #134 a fix was committed that ensures email notifications were aggregated, but this exposed another error. A notification type is designed to use it's own email template and so needs to be enqueued separately. This happened previously as notifications weren't aggregated, now they are they are not separated by type.

How to test

There's only one notification type currently defined, so as long as the tests pass I think it's good to merge 😄

@stephen-cox stephen-cox mentioned this pull request May 23, 2025
@finnlewis
Copy link
Member

Added a separate issue for the ESLint failures: #139

Copy link
Member

@finnlewis finnlewis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tests pass, (apart from for PHP 8.4)

@finnlewis finnlewis merged commit ac103ee into 1.x May 27, 2025
14 of 17 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Tests failure after merging #134
3 participants